Dec 03 17:37:25.742 INFO testing burst-pool-0.5.1 against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 03 17:37:25.742 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-4/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 17:37:26.087 INFO [stdout] c5f8d6e7875e3e6cd25a262511bdb11d04f1114534b13a214d90c55aea4ca682
Dec 03 17:37:26.093 INFO running `"docker" "start" "-a" "c5f8d6e7875e3e6cd25a262511bdb11d04f1114534b13a214d90c55aea4ca682"`
Dec 03 17:37:26.663 INFO [stderr] usermod: no changes
Dec 03 17:37:26.702 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 17:37:26.702 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 17:37:26.702 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 17:37:26.702 INFO [stderr] files will be included as a benchmark target:
Dec 03 17:37:26.702 INFO [stderr] 
Dec 03 17:37:26.702 INFO [stderr] * /source/benches/settings.rs
Dec 03 17:37:26.702 INFO [stderr] * /source/benches/stats.rs
Dec 03 17:37:26.702 INFO [stderr] 
Dec 03 17:37:26.702 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 17:37:26.702 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 17:37:26.702 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 17:37:26.702 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 17:37:26.702 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 17:37:26.702 INFO [stderr] 
Dec 03 17:37:26.702 INFO [stderr] For more information on this warning you can consult
Dec 03 17:37:26.702 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 17:37:26.738 INFO [stderr]    Compiling burst-pool v0.5.1 (/source)
Dec 03 17:37:27.607 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.92s
Dec 03 17:37:27.610 INFO [stderr] su: No module specific data is present
Dec 03 17:37:27.850 INFO running `"docker" "inspect" "c5f8d6e7875e3e6cd25a262511bdb11d04f1114534b13a214d90c55aea4ca682"`
Dec 03 17:37:27.909 INFO running `"docker" "rm" "-f" "c5f8d6e7875e3e6cd25a262511bdb11d04f1114534b13a214d90c55aea4ca682"`
Dec 03 17:37:27.978 INFO [stdout] c5f8d6e7875e3e6cd25a262511bdb11d04f1114534b13a214d90c55aea4ca682
Dec 03 17:37:27.981 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-4/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 17:37:28.171 INFO [stdout] 5f68ec06098e4b54a992ba279a70358cc685c4c1682b8c36ffe0ff4dfc29696b
Dec 03 17:37:28.174 INFO running `"docker" "start" "-a" "5f68ec06098e4b54a992ba279a70358cc685c4c1682b8c36ffe0ff4dfc29696b"`
Dec 03 17:37:28.451 INFO [stderr] usermod: no changes
Dec 03 17:37:28.471 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 17:37:28.471 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 17:37:28.471 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 17:37:28.471 INFO [stderr] files will be included as a benchmark target:
Dec 03 17:37:28.471 INFO [stderr] 
Dec 03 17:37:28.471 INFO [stderr] * /source/benches/settings.rs
Dec 03 17:37:28.471 INFO [stderr] * /source/benches/stats.rs
Dec 03 17:37:28.471 INFO [stderr] 
Dec 03 17:37:28.471 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 17:37:28.471 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 17:37:28.471 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 17:37:28.471 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 17:37:28.471 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 17:37:28.471 INFO [stderr] 
Dec 03 17:37:28.471 INFO [stderr] For more information on this warning you can consult
Dec 03 17:37:28.471 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 17:37:28.488 INFO [stderr]    Compiling spmc v0.2.2
Dec 03 17:37:28.969 INFO [stderr]    Compiling burst-pool v0.5.1 (/source)
Dec 03 17:37:30.076 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.61s
Dec 03 17:37:30.079 INFO [stderr] su: No module specific data is present
Dec 03 17:37:30.342 INFO running `"docker" "inspect" "5f68ec06098e4b54a992ba279a70358cc685c4c1682b8c36ffe0ff4dfc29696b"`
Dec 03 17:37:30.405 INFO running `"docker" "rm" "-f" "5f68ec06098e4b54a992ba279a70358cc685c4c1682b8c36ffe0ff4dfc29696b"`
Dec 03 17:37:30.460 INFO [stdout] 5f68ec06098e4b54a992ba279a70358cc685c4c1682b8c36ffe0ff4dfc29696b
Dec 03 17:37:30.462 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-4/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 17:37:30.582 INFO [stdout] 2759a9974ae95a899c6f15f1c07f175ef29ca897d69a269f51e71ee0f11600cd
Dec 03 17:37:30.584 INFO running `"docker" "start" "-a" "2759a9974ae95a899c6f15f1c07f175ef29ca897d69a269f51e71ee0f11600cd"`
Dec 03 17:37:30.878 INFO [stderr] usermod: no changes
Dec 03 17:37:30.899 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 17:37:30.899 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 17:37:30.899 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 17:37:30.899 INFO [stderr] files will be included as a benchmark target:
Dec 03 17:37:30.899 INFO [stderr] 
Dec 03 17:37:30.899 INFO [stderr] * /source/benches/settings.rs
Dec 03 17:37:30.899 INFO [stderr] * /source/benches/stats.rs
Dec 03 17:37:30.899 INFO [stderr] 
Dec 03 17:37:30.899 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 17:37:30.899 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 17:37:30.899 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 17:37:30.899 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 17:37:30.899 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 17:37:30.899 INFO [stderr] 
Dec 03 17:37:30.899 INFO [stderr] For more information on this warning you can consult
Dec 03 17:37:30.899 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 17:37:30.911 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Dec 03 17:37:30.912 INFO [stderr]      Running /target/debug/deps/burst_pool-2acc4e47c8fbbbbc
Dec 03 17:37:30.914 INFO [stdout] 
Dec 03 17:37:30.914 INFO [stdout] running 0 tests
Dec 03 17:37:30.914 INFO [stdout] 
Dec 03 17:37:30.914 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 17:37:30.914 INFO [stdout] 
Dec 03 17:37:30.914 INFO [stderr]    Doc-tests burst_pool
Dec 03 17:37:32.287 INFO [stdout] 
Dec 03 17:37:32.287 INFO [stdout] running 1 test
Dec 03 17:37:34.960 INFO [stdout] test lib.rs -  (line 66) ... ok
Dec 03 17:37:34.960 INFO [stdout] 
Dec 03 17:37:34.960 INFO [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 17:37:34.960 INFO [stdout] 
Dec 03 17:37:34.971 INFO [stderr] su: No module specific data is present
Dec 03 17:37:36.075 INFO running `"docker" "inspect" "2759a9974ae95a899c6f15f1c07f175ef29ca897d69a269f51e71ee0f11600cd"`
Dec 03 17:37:36.396 INFO running `"docker" "rm" "-f" "2759a9974ae95a899c6f15f1c07f175ef29ca897d69a269f51e71ee0f11600cd"`
Dec 03 17:37:36.734 INFO [stdout] 2759a9974ae95a899c6f15f1c07f175ef29ca897d69a269f51e71ee0f11600cd
